Handle integer replies, implement a connect timeout and dynamic config in VCL #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Please consider pulling the following patches (details available in the commit messages):
Noah Williamsson (6):
Handle REDIS_REPLY_INTEGER in vmod_call() and return it as a string
Initialize config (host, port) once per VCL instead of once every call
Implement a connect timeout for connecting to Redis, defaulting to 200ms
Allow the Redis server and timeout to be set in VCL via redis.init_redis()
Provide a commented out example of redis.init_redis() in examples/example.vcl
Fix typo in examples/example.vcl (redis.call -> redis.send)
Tested on 32- and 64-bit Linux aswell as Mac OS X with Varnish 3.0.2.